The Device Programmer/Monitor (Radio Management)

The Device Programmer component has two main functions: to Monitor for radio (Device) presence and to execute Programming jobs (Read and Write codeplugs and update firmware). The Device Monitor provides the user-interface to configure the Device Programmer and to view its current operations. Monitoring includes constantly listening for the presence of radios, and qualifying any detected radios as being a part of the same Radio Management system's radio fleet. Executing programming jobs includes matching detected Radio Management fleet radios with applicable and current Radio Management "Read" and "Write" events.

	Many Device Programmers are able to be installed within a single Radio Management (one Server) configuration, and are able to be run on multiple remotely-located computers / devices.
	The Device Programmer facilitates the processing of scheduled "Read" and "Write" jobs even when the computer is unattended or the user is not logged on.
	The Device Monitor's user-interface does not need to be running in order for scheduled jobs to be performed by the Device Programmer.
	When a Radio's status is No Manage Radio within the Device Monitor window, this indicates that the Device Programmer has detected the presence of this radio, however the radio is not part of the current Radio Management's fleet. If appropriate, the radio can be added to the Server database using one of the Radio Management Add Radios feature.

1.	From your Window's Taskbar, an icon is available to launch the Device Monitor Window. From your Window's Start menu under "Motorola" è "RM Device Programmer" è "RM Device Monitor" you may also launch this Device Monitor Window.
2.	The Device Monitor Window's "Settings" button allows you to view or modify Device Programmer connection settings to the RM Server.
3.	From the Device Monitor window you may define the Radio Connection Method of all jobs to be executed on that specific Device Programmer. Device Programmer-to-Radio communications can occur to one or several radios connected by USB cabling, either directly or via a battery-charging / programming station. *Fails to Detect: On a very rare occasion it is possible that a radio may fail to be detected*** by the Device Programmer. If this occurs, disconnect and power down the radio, then re-connect and power the radio on. On an even more rare occasion you may need to re-start the Device Programmer PC. OR Device Programmer-to-Radio communications can also occur over-the-air, via Over the Air Programming (OTAP). For OTAP requirements, see also: Programming for Radio Management OTAP
4.	When the Device Programmer's status is "Online", and when a radio's presence is detected, a scheduled job for the radio(s) is downloaded from the RM Server. Read and Write Jobs are created in the Radio Management Client's - Schedule a Job Window.
5.	If a radio's presence is detected and... a scheduled job's Date and Time interval for the radio falls within the current Data and Time, the job is downloaded from the RM Server and the job can occur. a scheduled job's Start Date and Time has passed but the End Date and Time has not passed, this is considered to be within the active job interval, the job is downloaded from the RM Server and the job can occur. a scheduled job's Date and Time interval for the radio falls outside of the current Data and Time, the job is not downloaded from the RM Server and therefore the job cannot occur.
6.	Jobs can only be cancelled from the Radio Management Client, "Cancel Job" selection; however, jobs cannot be cancelled once they have started.
7.	The Device Programmer allows the computer to program radios, regardless of whether a user is logged onto the computer or not; however the Device Programmer's Automatically Process Jobs feature can also be set to force jobs to be manually executed by the Radio Management-user.
8.	The Device Monitor Window allows you to view the status of radio programming jobs.

The Device Programmer / Monitor

(Radio Management)